System Requirements

Table 848: System Requirements provides the recommendations for minimum system specifications used by Keyfactor Command components. All servers may be deployed as virtual machines and may be part of a clustering or load-balanced architecture, if desired. If the Keyfactor Command roles are co-located, the specifications may need to be scaled accordingly. All Microsoft-supported methods for making SQL Server highly available are supported. For most high availability requirements, Keyfactor recommends using always on availability groups (see SQL Server).

Important:  SSHClosed The SSH (secure shell) protocol provides for secure connections between computers. It provides several options for authentication, including public key, and protects the communications with strong encryption. management in Keyfactor Command with the Keyfactor Bash OrchestratorClosed The Bash Orchestrator, one of Keyfactor's suite of orchestrators, is used to discover and manage SSH keys across an enterprise. (see SSH) is only supported when using Active Directory as an identity provider (see Selecting an Identity Provider for Keyfactor Command). The SSH option in the Management Portal will only appear when Keyfactor Command is installed using Active Directory as an identity provider (and with a license that supports SSH).

Table 848: System Requirements

Component

Minimum Requirements

Keyfactor Command Server
(Management Portal, Keyfactor API, and Services roles)

  • Windows Server 2019 or 2022

  • Internet Information Services (IIS) with:

    See Install IIS and .NET on the Keyfactor Command Server.

  • ASP.NET Core Hosting Bundle version 6.0 (x64). Version 6.0 is available for download from Microsoft:

    https://dotnet.microsoft.com/download/dotnet/6.0/runtime

    You need the ASP.NET Core Hosting Bundle, not the .NET Runtime (x64) or the ASP.NET Core Runtime. At the above link, this would be the Download Hosting Bundle option under the Run server apps heading.

    Figure 444: Select the Download Hosting Bundle Option Under Run Server Apps

    You can use the following PowerShell command to check the .NET core version(s) installed on a server (if any):

    dotnet --list-runtimes

    Output from this command will look something like this if you have the correct 6.0 x64 version of the .NET Hosting Bundle installed (notice the path is in C:\Program Files, not C:\Program Files (x86), indicating this is the x64 version):

    Microsoft.AspNetCore.App 6.0.21 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
    Important:  The ASP.NET Core Hosting Bundle should not be installed before installing IIS. If the hosting bundle is installed before IIS is installed, the bundle will not function correctly after the IIS install and will require repair.

  • .NET Framework 4.7.2 or greater

  • 4 GB RAM, 2 GHz CPU, 40 GB disk

  • Keyfactor Command license key for the current release

Microsoft SQL Database

Ability to connect to a Microsoft SQL Server 2017, 2019, or 2022 all with TLS encryption enabled and compatibility level 130 or higher.

8 GB RAM, 2+ GHz CPU (>= 2 cores), 500 GB disk
Browser to Access the Management Portal

  • Chrome: 99.0.4844.74+

  • Firefox: 98.0+

  • Microsoft Edge: 99.0.1150.30+
EJBCA CA (Optional)

  • EJBCA Enterprise version 7.8.1 or later is supported.

  • The EJBCA REST API must be enabled to interoperate with Keyfactor Command (see System Configuration -> Protocol Configuration in the EJBCA administration portal).